Added support for unquoted String Values #121
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In current version, you can enable unquoted keys by using
JsonOptions.AllowUnquotedKeys = True
, but that doesn’t capture unquoted values (except, of course, for reserved values like numbers ornull
). But it may happen that you find unquoted values for strings with just one word (I think that’s called relaxed json).Example:
{firstName: John, lastName: Smith}
I have update the code to cover those cases.
How to enable:
Just set the setting
JsonOptions.AllowUnquotedKeys
toTrue
, it will now also capture those 1-word unquoted String values.Implementation notes:
IsNumeric()
I convert the value back to number usingVBA.Val()
.Null
True
/False
Next steps:
We should clarify the setting
JsonOptions.AllowUnquotedKeys
: (a) rename it to clarify it works for both key and values or (b) create a new setting to allow unquote key/values separately.Thanks!